Deal with OhSilly threat levels. 🔼

The big one will be notecard reading and writing.

osGetAvatarList() I suspect is the other one I have to deal with.

reported=2019-07-03 16:54:17

reporter=onefang

priority=high

category=TODO

severity=major

resolution=fixed

2019-07-03 17:05:34 onefang: Depending on version of OpenSim and how it is configured, the detector might not pick up on the DEBUG_CHANNEL messages.  So doing the probe automatically might be good.  Or something like -

[code=LSL]

if (doSpeed)

{

doSpeed = FALSE;

osSetSpeed(...);

doSpeed = TRUE;

}

[/code]

Except that again, depending on version and configuration, the osSetSpeed() call may not fail out of that event like the probe expects.

By it's nature the probe will likely spew DEBUG_CHANNEL errors, perhaps a lot of them.  Would be very annoying to do that on every sim change.  Maybe on grid change?

2021-03-06 03:50:36 onefang: Naturally OpenSim changes the DEBUG messages for every version, so gotta track those.

2021-08-26 16:18:08 onefang: Three options.

[list]

[*]Trigger the OhSillyThreatDetector probe 30 seconds after things reset.  Cut down the list of things it's checking for to the bare minimum needed.

[*]On every [url=http://wiki.secondlife.com/wiki/CHANGED_REGION]CHANGED_REGION[/url] trigger the OhSillyThreatDetector probe.  Cut down the list of things it's checking for to the bare minimum needed.

[*]Have a list of functions we use set to unknown, works, denied.  Set them all to unknown each region change.  Try each one when needed if set to unknown.

[/list]